Rack server management

ABSTRACT

Techniques presented herein provide approaches for managing rack servers. In one embodiment, a message is received from a management controller of a rack server and via a switch port, where the message requests a lease for a network address under a first protocol. Upon determining that the management controller is a supported device, the switch port is configured to allow network traffic under at least a second protocol.

TECHNICAL FIELD

Embodiments presented in this disclosure generally relate to techniquesfor managing rack servers and, more particularly, to techniques forestablishing communication between a management application and one ormore rack servers.

BACKGROUND

As the number of computer servers used by businesses has substantiallyincreased, a number of techniques have been developed to remotely managethe operation of such servers. For example, large data centers arefrequently managed using a variety of different remote management tools,including, e.g., simple terminal connections, remote desktopapplications and sophisticated software tools used to configure,monitor, and troubleshoot both computer hardware and software. Theremote management tools are often configured to communicate using one ormore standardized protocols.

BRIEF DESCRIPTION OF THE DRAWINGS

To facilitate understanding of embodiments presented in this disclosure,the appended drawings are provided, which illustrate only typicalembodiments presented in this disclosure and are therefore not to beconsidered limiting of its scope, and which are briefly described asfollows.

FIG. 1 is a block diagram illustrating a system for managing rackservers, according to one embodiment.

FIG. 2 is a block diagram illustrating a system for managing the rackservers, according to one embodiment.

FIG. 3 is a flowchart depicting a method for managing the rack servers,from the perspective of a management application, according to oneembodiment.

FIG. 4 is a flowchart depicting a method for managing the rack servers,from the perspectives of both the management application and the rackservers, according to one embodiment.

DETAILED DESCRIPTION Overview

Embodiments presented in this disclosure provide a method, logic encodedin one or more tangible media, and system for performing an operationthat includes receiving a message from a management controller of a rackserver. The message requests a lease for a network address under a firstprotocol. Further, the message stores one or more parameterscharacterizing the management controller in one or more fields definedby the first protocol as being reserved for vendor-specific extensions.Further, the message is received via a switch port configured to allowonly network traffic under the first protocol. The operation alsoincludes providing the lease for the network address to the managementcontroller via the switch port. The operation also includes, upondetermining that the management controller is a supported device basedon the one or more parameters and an indication of one or more supporteddevices, configuring the switch port to allow network traffic under atleast a second protocol.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Embodiments presented in this disclosure provide techniques for managingrack servers. One embodiment provides an application that manages therack servers by communicating with management controllers in the rackservers using predefined protocols. In this regard, the application andthe management controllers may perform operations configured to monitorand control the health and performance of components of the rackservers. The operations may include monitoring elements such astemperatures, voltages, power supplies, fans, bus errors, etc. Forexample, the application (or management controller) may receive areading from a temperature sensor indicating that system temperature ina rack server is rising, and in response, send a command to increase fanspeed in the rack server. Further, the application may also log thetemperature reading. The application (or management controller) may alsobe configured to detect indications of a failed hardware component andgenerate an alert when a hardware component fails.

To this end, the management controller may communicate with componentsof the rack server using messages composed according to the IntelligentPlatform Management Interface (IPMI) specification. IPMI refers tomonitoring, system control and communication interfaces implementeddirectly in platform management hardware and firmware (e.g., thehardware and firmware of the host computer). Further, the managementcontroller of the rack server may run on standby power, even when thehost processors of the rack server are powered down. Examples of amanagement controller include a baseboard management controller (BMC)and a lights out management system. Using the techniques disclosedherein, the application identifies, authenticates, authorizes and/ormanages the rack servers without requiring any user intervention.Accordingly, the application may manage the rack servers moreconveniently and/or efficiently at least in some cases.

FIG. 1 is a block diagram illustrating a system 100 for managing rackservers 160, according to one embodiment. The networked system 100includes a computer 102. The computer 102 may also be connected via thenetwork 130 to other computers, such as the rack servers 160.Additionally or alternatively, the computer 102 may be connected to oneor more blade servers. In general, the network 130 may betelecommunications network and/or a wide area network (WAN). In oneembodiment, the network 130 is the Internet.

The computer 102 generally includes a processor 104 connected via a bus112 to a memory 106, a network interface device 110, a storage 108, aninput device 114, and an output device 116. The computer 102 isgenerally under the control of an operating system. Examples ofoperating systems include UNIX, versions of the Microsoft Windows®operating system, and distributions of the Linux® operating system. Moregenerally, any operating system supporting the functions disclosedherein may be used. The processor 104 is included to be representativeof a single CPU, multiple CPUs, a single CPU having multiple processingcores, and the like. Similarly, the memory 106 may be a random accessmemory. While the memory 106 is shown as a single identity, it should beunderstood that the memory 106 may comprise a plurality of modules, andthat the memory 106 may exist at multiple levels, from high speedregisters and caches to lower speed but larger DRAM chips. The networkinterface device 110 may be any type of network communications deviceallowing the computer 102 to communicate with other computers via thenetwork 130.

The storage 108 may be a persistent storage device. Although the storage108 is shown as a single unit, the storage 108 may be a combination offixed and/or removable storage devices, such as fixed disc drives, solidstate drives, floppy disc drives, tape drives, removable memory cards oroptical storage. The memory 106 and the storage 108 may be part of onevirtual address space spanning multiple primary and secondary storagedevices.

The input device 114 may be any device for providing input to thecomputer 102. For example, a keyboard and/or a mouse may be used. Theoutput device 116 may be any device for providing output to a user ofthe computer 102. For example, the output device 116 may be anyconventional display screen or set of speakers. Although shownseparately from the input device 114, the output device 116 and inputdevice 114 may be combined. For example, a display screen with anintegrated touch-screen may be used.

As shown, the memory 106 of the computer 102 includes an application150, and each rack server 160 includes a respective managementcontroller 162. The application 150 is configured to manage the rackservers 160 by communicating with the management controllers 162 via thenetwork 130, using one or more predefined protocols. The application 150may also provide a command-line interface (CLI), a graphical userinterface (GUI), and/or an application programming interface (API) formanaging the rack servers 160. In some embodiments, the computer 102 isconfigured to provide a switch fabric for the rack servers 160. In thisregard, the computer 102 may be configured to provide some or allfunctionality typically provided by a network switch. As used herein, aswitch fabric refers to a network topology where network nodes connectwith each other via one or more network switches. In this regard, thecomputer 102 may be regarded as a fabric interconnect device, or fabricinterconnect for short. Further, the storage 108 of the computer 102stores supported device data 152 and an inventory 154.

In one embodiment, the supported device data 152 characterizes whichmanagement controllers 162 are deemed to be valid devices by theapplication 150. Put another way, the supported device data 152 includesindications of which management controllers 162 are deemed to be validor supported by the application 150. The supported device data 152 maystore one or more fields identifying different devices and/or devicetypes and an associated flag indicating whether each device and/ordevice type is supported. In one embodiment, a valid or supported devicerefers to a device that is compatible with the functionality of theapplication 150 for identifying, authenticating, authorizing and/ormanaging the rack servers 160 as disclosed herein. The application 150uses the supported device data 152 in managing the rack servers 160,such as in authorizing and/or authenticating the management controllers162 of the rack servers 160. For example, the application 150 maycompare parameters received from and characterizing the managementcontroller 162 with the fields stored in the supported device data 152,to determine whether the management controller 162 is a supporteddevice. The application 150 also maintains the inventory 154 of the rackservers 160 and/or management controllers 162.

FIG. 2 is a block diagram illustrating a system 200 for managing therack servers 160, according to one embodiment. As shown, the networkedsystem 200 includes two fabric interconnects 202, two fabric extenders206, and the rack servers 160. As shown, the networked system 200provides an in-band network 216 ₁ and an out-of-band network 216 ₂. Thein-band network 216 ₁ provides network connectivity to the rack servers160, and the out-of-band network 216 ₂ is an independent networkdedicated for managing components of the rack servers 160, regardless ofwhether the rack servers 160 are reachable via the in-band network 216₁. For example, a rack server 160 may not be reachable via in-bandnetwork 216 ₁ when a problem occurs with a component of the in-bandnetwork 216 ₁, such as a switch, router or the rack server 160.

In one embodiment, configuring the networked system 200 to include twofabric interconnects 202 and/or two fabric extenders 206 providesredundant network paths for both management traffic and data traffic.Each fabric interconnect 202 corresponds to the computer 102 of FIG. 1.Further, each fabric extender 206 is configured to extend a switchfabric provided by a respective fabric interconnect 202 and may includeone or more switch ports. In this regard, each fabric extender 206serves as remote line cards for an associated fabric interconnect 202.In one embodiment, a line card refers to a card or assembly thatcontains data interfaces (e.g., optical fibers) and which may beinserted into a network device, such as a switch or router. Each fabricinterconnect 202 may also manage configurations of the associated fabricextender 206.

As shown, each rack server 160 is connected to the in-band network 216 ₁via cabling from a network adapter port 214 to a switch port 204 of thefabric interconnect 202. Further, each rack server 160 is connected tothe out-of-band network 216 ₂ via cabling from a LAN on motherboard(LOM) port 212 to the fabric extender 206 and cabling from the fabricextender 206 to another switch port 204 of the fabric interconnect 202.In an alternative embodiment, each rack server 160 is connected to theout-of-band network 216 ₂ via cabling from the LOM port 212 to thefabric interconnect 202 and not through any fabric extender 206. In aparticular embodiment, each fabric interconnect 202 may be a Cisco® UCS6100 series fabric interconnect, each fabric extender 206 may be aCisco® Nexus 2000 series fabric extender, and the application executingon each fabric interconnect 202 may be a Cisco® Unified Computing SystemManager (UCSM).

In one embodiment, each management controller 162 maintains a state,where the state stores an operating mode of the respective managementcontroller 162. Each management controller 162 operates in either a“stand-alone” operating mode or a “UCSM” operating mode. The stand-aloneoperating mode indicates that the management controller 162 is notcurrently attempting to parse any commands from the application 150. TheUCSM operating mode indicates that the management controller 162 iscurrently attempting to parse commands from the application 150. Theapplication 150 may instruct the management controller 162 to transitionbetween the two operating modes.

In one embodiment, the application 150 configures each managementcontroller 162 with a respective network address for the out-of-bandnetwork 216 ₂ using a predefined protocol. Depending on the embodiment,the predefined protocol may either be vendor-specific orvendor-independent. A vendor-independent protocol refers to a protocolthat is not specific to any vendor. In one embodiment, each networkaddress is an Internet Protocol (IP) address, and the predefinedprotocol is Dynamic Host Configuration Protocol (DHCP). Further, theapplication 150 may also provide a DHCP service for the managementcontrollers 162. Depending on the embodiment, some or all of thefunctionality of the DHCP service may be provided by a separate programassociated with and/or managed by the application 150, and vice versa.By default, each management controller 162 may be configured to send, tothe DHCP service, one or more DHCP messages requesting an IP addressfrom the DHCP service. The DHCP messages include a field storing aclient identifier. The client identifier may be composed according to apredefined format that is customizable by a vendor of the application150, to suit the needs of a particular case. Table I shows an example ofa predefined format for the client identifier.

TABLE I Example format for a client identifier in a DHCP message<VENDOR>|+|<MODEL>|+|<SERIAL>

As shown, the predefined format for the client identifier includes threesub-fields separated by a predefined delimiter (“|+|”). The threesub-fields include a vendor identifier, a model identifier, and a serialidentifier. In one embodiment, the application 150 uses the vendoridentifier and the model identifier to identify a source of the DHCPmessages as a valid device, where the source is a rack server 160 and/ora management controller 162. The application 150 uses the serialidentifier to maintain the inventory 154 of identified devices. Theinventory 154 is maintained for audit and/or authentication purposes. Inparticular, the application 150 uses the inventory 154 to associatefeatures and/or configurations to a particular rack server 160. Forinstance, suppose that a rack server 160, having an associatedconfiguration, is decommissioned for maintenance and is subsequentlyreconnected to the switch fabric following a maintenance cycle. Theapplication 150 may then identify the rack server 160 and re-associatethe configuration with the rack server 160. In some embodiments, theinventory is stored in a database system, and the serial identifier maybe used as a unique key in the database system. In other embodiments,the serial identifier is combined with an additional field, such as aproduct identifier field, to form the unique key.

In one embodiment, the DHCP messages sent by the management controller162 further contain one or more parameters characterizing the managementcontroller 162. The parameters may be stored in one or more fields thatare reserved for vendor-specific extensions. For example, the fields maycorrespond to one or more options within the range of DHCP options224-254, which is designated by the DHCP specification as being reservedfor vendor-specific extensions.

In one embodiment, the DHCP messages sent by the application 150 and/orDHCP service may also store data in one or more fields that are reservedfor vendor-specific extensions. For example, suppose the managementcontroller 162 sends a message requesting DHCP option 251. In response,the application 150 and/or DHCP service sends one or more messageshaving a field corresponding to DHCP option 251 and storing data in apredefined format, such as shown in Table II.

TABLE II Example data stored in DHCP option 251 by the application<ucsmdata version=”1 0”>   <action name=”change-mode” val=”ucsm”/>  <auth hashval=”123” count=”23”/> </ucsmdata>

As shown in Table II, the data stored in DHCP option 251 includes aprotocol version, a command and an authentication token. The protocolversion specifies a version of the protocol being used by the DHCPserver for identifying the management controllers 162. As shown, theprotocol version is specified in the <ucsmdata> tag as being version1.0. The <ucsmdata> tag additionally identifies the DHCP server as thesource of the message. The command, specified in an <action> tag,instructs the management controller 162 to transition to the UCSMoperating mode. The authentication token is specified in an <auth> tag.Other commands are broadly contemplated. For example, the other commandsmay specify to reset the management controller 162, to restore aconfiguration of the management controller 162 to a factory defaultconfiguration, etc.

In one embodiment, the management controller 162 parses the data toretrieve the commands, authentication tokens, etc. The managementcontroller 162 may also execute the retrieved commands. In oneembodiment, the format for data stored in the DHCP option 251 may beproprietary to a vendor of the application 150 or of the fabricinterconnect 202. Because the DHCP specification does not mandate theuse of DHCP option 251, applications and/or DHCP services from othervendors will likely either not populate the data or populate the dataincorrectly. In such cases, the management controller 162 will notsuccessfully parse any commands from the DHCP option 251.

In one embodiment, the management controllers 162 may respond tomessages sent from the DHCP service. For example, the managementcontrollers 162 may send additional messages that store data in one ormore options within the range of DHCP options 224-254. The DHCP servicemay parse the data in the additional messages to complete a process ofdiscovering and/or maintaining an inventory for the rack servers 160.

For example, suppose that the management controller 162 sends a messageto the DHCP service, where the message requests to the DHCP service topopulate DHCP option 250. Table III shows an example of the message sentto the DHCP service.

TABLE III Example data stored in DHCP option 250 by the managementcontroller <bmcdata version “1 0” mode=″stand-alone″ source=″lom″>  <auth hashval=″10023″ count=″67″/> </bmcdata>

As shown in Table III, the data stored in DHCP option 250 includes aprotocol version, an operating mode, a source interface and anauthentication token. The protocol version is specified in the <bmcdata>tag as being version 1.0. The <bmcdata> tag additionally identifies themanagement controller 162 as being the source of the message. Theoperating mode, specified in the <mode> tag, indicates that themanagement controller 162 is currently operating in the stand-alonemode. The source interface, specified in the <source> tag, identifiesthe physical interface being used to connect the rack server 160 to thefabric interconnect 202. In this particular example, the physicalinterface is the LOM. By configuring the DHCP service according to thetechniques disclosed herein, the DHCP service may parse the DHCP option250 in the message, to retrieve the hash value contained in the message.A DHCP service not so configured will likely ignore the DHCP option 250,without any impact to functionality to the DHCP service. Accordingly, alevel of compatibility with other DHCP services is maintained.

In one embodiment, responsive to messages requesting an IP address, theDHCP service provides, to the management controller 162, a lease for theIP address for the out-of-band network 216 ₂. Additionally, the DHCPservice may also update an entry for the management controller, in theinventory 154. Further, the DHCP service may also monitor a state of themanagement controller 162 and/or rack server 160. In one embodiment, theduration of a lease may be a predefined number of seconds. Having arelatively short lease duration—such as one of several seconds—resultsin the management controller 162 requesting a new lease more frequently.Increasing a frequency which a management controller 162 communicateswith the DHCP service is advantageous at least in some cases, becausedoing so allows the management controller 162 to communicate any changeof state of the management controller 162 and/or of rack server 160 morefrequently.

In one embodiment, the application 150 is further configured to managethe switch ports 204 and/or the switch ports of the fabric extenders206. To this end, the application 150 may maintain a state for eachswitch port, where the state is either an “untrusted” state or a“trusted” state. For instance, the application 150 may designate aswitch port 204 as being in an untrusted state. In the untrusted state,the switch port 204 is configured to allow only DHCP packets to and/orfrom the management controller 162. Upon identifying the managementcontroller 162 as a valid device, the application 150 may additionallydesignate the switch port 204 as being in a trusted state. In thetrusted state, the switch port 204 is configured to allow packets of oneor more predefined protocols other than DHCP—in addition to allowingDHCP packets to and/or from the management controller 162. The one ormore predefined protocols may include Secure Shell (SSH), Telnet,Hypertext Transfer Protocol (HTTP), HTTP Secure (HTTPS), Trivial FileTransfer Protocol (TFTP) and Intelligent Platform Management Interface(IPMI), etc.

In some embodiments, in the trusted state, the switch port 204 allowsall types of network traffic to and/or from the management controller162. Once the switch port 204 is in the trusted state, the application150 may further authenticate and/or authorize the management controller162 using one or more additional protocols. The additional protocols maybe proprietary to the vendor of the application 150 and may be tailoredto suit the needs of a particular case. For instance, the application150 may issue one or more commands via a mctools protocol. The mctoolsprotocol refers to a proprietary protocol configured to support commandssuch as retrieving sensor readings from the management controller 162,retrieving logs from the management controller 162, executing poweroperations via the management controller 162, etc.

In one embodiment, the switch port 204 may also revert from a trustedstate to an untrusted state. For example, the application 150 may revertthe switch port 204 from the trusted state to the untrusted state upondetecting that a user has removed, from the switch fabric, the rackserver 160 previously connected to the switch port 204. As anotherexample, the application 150 may revert the switch port 204 from thetrusted state to the untrusted state upon detecting an indication that atopology change has occurred in the switch fabric. For instance, theindication may be a port flap for a switch port. Accordingly, by usingthe techniques disclosed herein, the application 150 may manage the rackservers 160 more securely at least in some cases.

FIG. 3 is a flowchart depicting a method 300 for managing the rackservers 160, from the perspective of the application 150, according toone embodiment. As shown, the method 300 begins at step 310, where theapplication 150 receives, via a switch port 204 and from a managementcontroller 162, a message requesting a lease for a network address forthe out-of-band network 216 ₂. The lease may be requested under apredefined protocol defining one or more fields reserved forvendor-specific extensions. In one embodiment, the switch port 204allows only network traffic using the predefined protocol. Further, themessage may store, in the fields reserved for vendor-specificextensions, parameters characterizing the management controller 162.

At step 320, the application 150 provides the management controller 162with the lease for the network address, responsive to the message andvia the predefined protocol. At step 330, the application 150 determineswhether the management controller 162 is a valid device, based on one ormore of the parameters received in the request (and a predefined set ofvalid devices). At step 340, upon determining that the managementcontroller 162 is a valid device, the application 150 configures theswitch port to further allow network traffic under at least one protocolother than the predefined protocol.

FIG. 4 is a flowchart depicting a method 400 for managing the rackservers 160, from the perspectives of both the application 150 and therack servers 160, according to one embodiment. As described above, theapplication 150 provides the DHCP service for the rack servers. Asshown, the method 400 begins at step 410, where the managementcontroller 162 of a rack server 160 connects to the DHCP service. At thestep 410, the management controller 162 also sends a message to the DHCPservice requesting an IP address. The DHCP message may include a clientidentifier and a populated DHCP option 250. The DHCP message may alsorequest DHCP option 251 from the DHCP service. At step 420, the DHCPservice receives the DHCP message.

At step 430, the DHCP service identifies the rack server 160 by usingthe client identifier and updates the database with a unique key and astate of the management controller 162. At step 440, the DHCP servicesends a response message to the management controller 162, to provide alease to the management controller 162. The response message populatesDHCP option 251 with one or more commands. At step 450, the managementcontroller 162 parses the response message from the DHCP service. Atstep 460, the management controller 162 determines whether the responsemessage includes DHCP option 251 data. If so, the management controller162 executes the one or more commands in the DHCP option 251 (step 470).Otherwise, at step 480, the management controller 162 and theapplication 150 complete the authentication process. At step 490, theapplication 150 converts the switch port 204 connected to the managementcontroller 162 from an untrusted state to a trusted state, allowingother non-DHCP traffic through the switch port 204.

Advantageously, embodiments described above provide approaches formanaging rack servers. In one embodiment, an application receives amessage from a management controller of a rack server and via a switchport, where the message requests a lease for a network address under afirst protocol. Upon determining that the management controller is avalid device, the application configures the switch port to allownetwork traffic under at least a second protocol. Accordingly, theapplication may manage the rack servers more conveniently and/orsecurely at least in some cases.

For example, the rack servers may be managed more conveniently and/orsecurely, relative to some alternative embodiments, which are furtherdescribed below. In particular, the application may support automaticdiscovery of rack servers, relative to such alternative embodiments,where automatic discovery refers to identifying the rack servers withoutrequiring user input and without requiring agents to be installed on therack servers, when compared to such alternative embodiments. Theapplication may also support asynchronous discovery of rack servers,relative to such alternative embodiments, where asynchronous discoveryrefers to identifying rack servers being added to the switch fabric,without requiring user input and without requiring agents to beinstalled on the rack servers. In this regard, the applicationidentifies the rack server without requiring any user intervention orscheduling mechanism. Merely the rack server being added to the switchfabric may be sufficient for prompting the application to identify therack server, and no other synchronization is required between theapplication and the operation of adding the rack server to the switchfabric.

An example of one such alternative embodiment includes installing anagent on each rack server, where the agent is a Simple NetworkManagement Protocol (SNMP) agent or a vendor-specific agent. Thealternative embodiment may also include having a user provide a range ofnetwork addresses in the switch fabric. The alternative embodiment mayalso include scanning the range of network addresses to identify allrack servers having the agent installed. The alternative embodiment mayalso include having a user manually provide authentication informationfor configuring the rack server and the application, such that the rackserver may communicate with the application via a secure protocol.

Additionally or alternatively, the application may also manage one ormore blade servers in a blade system. In the case of blade servers,however, a fixed relationship may be established between each chassisslot of a blade system and an IP address of a management controller ofthe blade server disposed within the respective chassis slot. Forexample, the IP address of the management controller may be determinedfrom a chassis identifier and a slot identifier for the chassis slot inwhich the blade server is disposed. Accordingly, the IP address of themanagement controller cannot be changed unless the blade server is movedto a different chassis slot of the blade system. This is in contrast tothe rack server environment, where no such relationship exists thatestablishes the IP address for the management controller. Consequently,the application may manage the blade servers more conveniently thanmanaging the rack servers at least in some cases.

In the preceding, reference is made to embodiments presented in thisdisclosure. However, it should be understood that the present disclosureis not limited to specific, described embodiments. Instead, anycombination of the following features and elements, whether related todifferent embodiments or not, is contemplated to implement and practicethe present disclosure, and moreover the disclosure is to be accordedthe widest scope consistent with the principles and features describedherein. Furthermore, although embodiments may achieve advantages overother possible solutions and/or over the prior art, whether or not aparticular advantage is achieved by a given embodiment is not limitingof the disclosure.

As will be appreciated by one skilled in the art, embodiments presentedin this disclosure be embodied as a system, method or computer programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a computer program product embodied inone or more computer readable medium(s) having computer readable programcode embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus or device.

Further, embodiments may be provided to end users through a cloudcomputing infrastructure. Cloud computing generally refers to theprovision of scalable computing resources as a service over a network.More formally, cloud computing may be defined as a computing capabilitythat provides an abstraction between the computing resource and itsunderlying technical architecture (e.g., servers, storage, networks),enabling convenient, on-demand network access to a shared pool ofconfigurable computing resources that can be rapidly provisioned andreleased with minimal management effort or service provider interaction.Thus, cloud computing allows a user to access virtual computingresources (e.g., storage, data, applications, and even completevirtualized computing systems) in “the cloud,” without regard for theunderlying physical systems (or locations of those systems) used toprovide the computing resources.

Typically, cloud computing resources are provided to a user on apay-per-use basis, where users are charged only for the computingresources actually used (e.g., an amount of storage space consumed by auser or a number of virtualized systems instantiated by the user). Auser can access any of the resources that reside in the cloud at anytime, and from anywhere across the Internet. In context of the presentdisclosure, the application and/or the management controllers mayoperate in the cloud. Doing so allows the user to manage execution ofthe rack servers from any computing system attached to a networkconnected to the cloud (e.g., the Internet).

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality and operation of possible implementations ofsystems, methods and computer program products according to variousembodiments presented in this disclosure. In this regard, each block inthe flowchart or block diagrams may represent a module, segment orportion of code, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved.

In view of the foregoing, the scope of the present disclosure isdetermined by the claims that follow.

1. A method comprising: receiving a message from a management controllerof a rack server, the message requesting a lease for a network addressunder a first protocol, the message storing one or more parameterscharacterizing the management controller in one or more fields definedby the first protocol as being reserved for vendor-specific extensions,and the message being received via a switch port configured to allowonly network traffic under the first protocol; providing the lease forthe network address to the management controller via the switch port;and upon determining that the management controller is a supporteddevice based on the one or more parameters and an indication of one ormore supported devices, configuring the switch port to allow networktraffic under at least a second protocol.
 2. The method of claim 1,further comprising: sending a request to the management controller viathe second protocol.
 3. The method of claim 2, wherein the requestcomprises at least one of: (i) a request for the management controllerto undergo further authentication; (ii) a request for the managementcontroller to execute a specified command; and (iii) a request for themanagement controller to retrieve a system parameter.
 4. The method ofclaim 1, wherein the message stores at least one of a vendor field, amodel field, and a serial number.
 5. The method of claim 4, whereindetermining the management controller is supported is based on at leastone of the vendor field and the model field, and wherein the serialfield is used to uniquely identify the management controller relative toother management controllers.
 6. The method of claim 1, wherein thefirst protocol comprises a vendor-independent protocol, and wherein thesecond protocol comprises a vendor-specific protocol.
 7. The method ofclaim 1, wherein determining the management controller is a supporteddevice comprises: comparing the one or more parameters with theindication of one or more supported devices.
 8. Logic encoded in one ormore tangible media for execution and when executed operable to: receivea message from a management controller of a rack server, the messagerequesting a lease for a network address under a first protocol, themessage storing one or more parameters characterizing the managementcontroller in one or more fields defined by the first protocol as beingreserved for vendor-specific extensions, and the message being receivedvia a switch port configured to allow only network traffic under thefirst protocol; provide the lease for the network address to themanagement controller via the switch port; and upon determining that themanagement controller is a supported device based on the one or moreparameters and an indication of one or more supported devices, configurethe switch port to allow network traffic under at least a secondprotocol.
 9. The logic of claim 8, further operable to: send a requestto the management controller via the at least one protocol other thanthe protocol.
 10. The logic of claim 9, wherein the request comprises atleast one of: (i) a request for the management controller to undergofurther authentication; (ii) a request for the management controller toexecute a specified command; and (iii) a request for the managementcontroller to retrieve a system parameter.
 11. The logic of claim 8,wherein the message stores at least one of a vendor field, a modelfield, and a serial number.
 12. The logic of claim 11, whereindetermining the management controller is supported is based on at leastone of the vendor field and the model field, and wherein the serialfield is used to uniquely identify the management controller relative toother management controllers.
 13. The logic of claim 8, wherein thefirst protocol comprises a vendor-independent protocol, and wherein thesecond protocol comprises a vendor-specific protocol.
 14. The logic ofclaim 8, wherein determining the management controller is a supporteddevice comprises: comparing the one or more parameters with theindication of one or more supported devices.
 15. A system comprising:one or more computer processors; logic encoded in one or more tangiblemedia for execution and, when executed by the one or more computerprocessors, operable to: receive a message from a management controllerof a rack server, the message requesting a lease for a network addressunder a first protocol, the message storing one or more parameterscharacterizing the management controller in one or more fields definedby the first protocol as being reserved for vendor-specific extensions,and the message being received via a switch port configured to allowonly network traffic under the first protocol; provide the lease for thenetwork address to the management controller via the switch port; andupon determining that the management controller is a supported devicebased on the one or more parameters and an indication of one or moresupported devices, configure the switch port to allow network trafficunder at least a second protocol.
 16. The system of claim 15, whereinthe logic is further operable to: send a request to the managementcontroller via the at least one protocol other than the protocol. 17.The system of claim 16, wherein the request comprises at least one of:(i) a request for the management controller to undergo furtherauthentication; (ii) a request for the management controller to executea specified command; and (iii) a request for the management controllerto retrieve a system parameter.
 18. The system of claim 15, wherein themessage stores at least one of a vendor field, a model field, and aserial number.
 19. The system of claim 18, wherein determining themanagement controller is supported is based on at least one of thevendor field and the model field, and wherein the serial field is usedto uniquely identify the management controller relative to othermanagement controllers.
 20. The system of claim 15, wherein the firstprotocol comprises a vendor-independent protocol, and wherein the secondprotocol comprises a vendor-specific protocol.